Domains as a Prerequisite for Requirements and Software Domain Perspectives & Facets, Requirements Aspects and Software Views

We take software systems] engineering to consist of three major phases: domain engineering , requirements engineering and software systems] design engineering. We outline these and emphasise domain perspectives andfacets, requirements aspects and software architecture and program organisation views. This paper is the direct result of a US OOce of Army Research October 12{14, 1997 workshop on Requirements Targeting Software and Systems Engineering held at Bernried am Staarnberger See, Bavaria, Germany. In consonance with the aims & objectives of that workshop we conclude some subsections with a set of meta{requirements (i.e. requirements to software engineering, its research, education and practice). The paper is discursive and informal: we identify a number of methodological principles , techniques and tools. Not all such (hence discursive) and not all necessarily for-malisable (hence informal). Wrt. the latter: one cannot formalise the principles that are needed in a systematic, well-guided process of selecting and applying techniques and tools in the analysis and synthesis of speciications | whether of domain, requirements or software. Instead we are left to conjecture the usefulness of certain such principles, techniques and tools. Sometimes such conjectures are refuted when better principles, techniques and tools are proposed. Some sociological issues of`formal methods' are summarised (in section 4.5). Since this paper will appear in a workshop proceedings with a number of other papers from that workshop, the paper will not repeat the relevant points made by other workshop participants and supposedly published in their contributions. I refer, amongst several, to contributions made at the workshop